Why Does FastChip DeviceLink (FDL) or ‘csoc download’
Fail on Windows ME?

If you are using Windows Millennium Edition (ME) and FDL or one of the FastChip command-line download/debug commands and the system seems to hang or is unresponsive, then you most likely have encountered a known FastChip 2.1.2 problem.

The root cause of this problem is a conflict with the Universal Plug-and-Play (UPnP) driver.  When UPnP is installed, a device driver called SSDPSRV.exe is activated on startup.  SSDPSRV.exe opens TCP/IP ports 1900 and 5000 and then listens on them.  Port 5000 is used to communicate to a website, and Explorer receives responses back on port 1900.  Port 5000 is also the default communication port for Triscend’s low-level JTAG driver called Spiderd.

Because Spiderd is also used when the Keil dScope debugger communicates with a Triscend E5 device, there can be similar symptoms when using Keil.

Here are two potential remedies for this problem.

Uninstall Universal Plug-and-Play (UPnP)

If you are not using Universal Plug-and-Play (UPnP), uninstall UPnP on your computer.  Click Start à Settings à Control Panel à Add/Remove Programs.

Locate and click the Microsoft Universal Plug-and-Play program in the list of program.  Click the Add/Remove button.

This fixes the problem with no further effort and no known side effects.

Re-assign to a Different Port

By default, both FastChip and Spiderd use TCP/IP port 5000 for communication with an E5 device.  This port conflicts with UPnP.

You can re-assign the default port numbers as shown below.

If FastChip or FDL is currently running, close the application.

In your FastChip installation directory, create a new file called triscend.props, if one does not already exist.

Using your favorite text edit, add the following line to the triscend.props file.  Choose a port between 5001 and 5009.  The examples below all use 5002

Triscend.defaultSpiderPort=5002

Save the triscend.props file.

Add and set a Windows ME system environment variable to SPIDER_PORT = 5002.

Modifying dScope Debugger Port Options

If you are using Keil uVision-2 dScope debugger, you also need to modify the default port settings there as well.  The following assumes that Keil uVision-2 is correctly installed on your computer.

With your Keil project open, select Project à Options for Target from the menu.

Click the Debug tab.

Click the Settings button next to the Triscend E5 Driver selection.

From the resulting dialog box, select a valid option from the Port droplist.  In this example, use port 5002.

Click OK to save your port settings.  Click OK again to save your target options.

© 2001 by Triscend Corporation.  All rights reserved.